CVE-2026-46417
Angular: SSRF via Hostname Hijacking in @angular/platform-server
Description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22, a Server-Side Request Forgery (SSRF) vulnerability exists in @angular/platform-server. The issue stems from how the server-side rendering (SSR) engine processes the request URL provided to the rendering entry points. When an absolute-form URL (e.g., http://evil.com) is passed to the rendering engine, the internal ServerPlatformLocation can be manipulated into adopting the attacker-controlled domain as the "current" hostname. Consequently, any relative HttpClient requests or PlatformLocation.hostname references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services. This vulnerability is fixed in 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22.
INFO
Published Date :
June 22, 2026, 3:40 p.m.
Last Modified :
June 22, 2026, 3:48 p.m.
Remotely Exploit :
No
Source :
GitHub_M
Solution
- Update @angular/platform-server to version 19.2.22 or later.
- Update @angular/platform-server to version 20.3.21 or later.
- Update @angular/platform-server to version 21.2.13 or later.
- Update @angular/platform-server to version 22.0.0-next.12 or later.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-46417 vulnerability anywhere in the article.